SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Serial presence detect</title>

</head>

Serial presence detect

</h1>

</header>

In <a href="Computing" title="Computing">computing</a>, serial presence detect (SPD) is a standardized way to automatically access information about a <a href="Memory_module" title="Memory module">memory module</a>. Earlier 72-pin <a href="SIMM" title="SIMM">SIMMs</a> included five pins that provided five bits of parallel presence detect (PPD) data, but the 168-pin <a href="DIMM" title="DIMM">DIMM</a> standard changed to a serial presence detect to encode more information.<a href="#cite_note-1">[1]</a>

When an ordinary modern computer is turned on, it starts by doing a <a href="Power-on_self-test" title="Power-on self-test">power-on self-test</a> (POST). Since about the mid-1990s, this process includes automatically configuring the hardware currently present. SPD is a memory hardware feature that makes it possible for the computer to know what memory is present, and what <a href="Memory_timings" title="Memory timings">memory timings</a> to use to access the memory.

Some computers adapt to hardware changes completely automatically. In most cases, there is a special optional procedure for accessing <a href="BIOS" title="BIOS">BIOS</a> parameters, to view and potentially make changes in settings. It may be possible to control how the computer uses the memory SPD data—to choose settings, selectively modify memory timings, or possibly to completely override the SPD data (see <a href="Overclocking" title="Overclocking">overclocking</a>).

<div class="mw-heading mw-heading2"><h2 id="Stored_information">Stored information</h2></div>

For a memory module to support SPD, the <a href="JEDEC" title="JEDEC">JEDEC</a> standards require that certain parameters be in the lower 128 bytes of an <a href="EEPROM" title="EEPROM">EEPROM</a> located on the memory module. These bytes contain timing parameters, manufacturer, serial number and other useful information about the module. Devices utilizing the memory automatically determine key parameters of the module by reading this information. For example, the SPD data on an <a href="SDRAM" class="mw-redirect" title="SDRAM">SDRAM</a> module might provide information about the <a href="CAS_latency" title="CAS latency">CAS latency</a> so the system can set this correctly without user intervention.

The SPD EEPROM firmware is accessed using <a href="SMBus" class="mw-redirect" title="SMBus">SMBus</a>, a variant of the <a href="I2C" class="mw-redirect" title="I2C">I2C</a> protocol. This reduces the number of communication pins on the module to just two: a clock signal and a data signal. The EEPROM shares ground pins with the RAM, has its own power pin, and has three additional pins (SA0–2) to identify the slot, which are used to assign the EEPROM a unique address in the range 0x50–0x57. Not only can the communication lines be shared among 8 memory modules, the same SMBus is commonly used on motherboards for system health monitoring tasks such as reading power supply voltages, <a href="Central_processing_unit" title="Central processing unit">CPU</a> temperatures, and fan speeds.

SPD EEPROMs also respond to I2C addresses 0x30–0x37 if they have not been write protected, and an extension (TSE series) uses addresses 0x18–0x1F to access an optional on-chip temperature sensor. All those values are <a href="I2C" class="mw-redirect" title="I2C">seven-bit I2C addresses</a> formed by a Device Type Identifier Code prefix (DTIC) with SA0-2: to read (1100) from slot 3, one uses <code>110 0011 = 0x33</code>. With a final R/W bit it forms the 8-bit Device Select Code.<a href="#cite_note-2">[2]</a> Note that the semantics of slot-id is different for write-protection operations: for them they can be not passed by the SA pins at all.<a href="#cite_note-3">[3]</a>

Before SPD, memory chips were spotted with parallel presence detect (PPD). PPD used a separate pin for each bit of information, which meant that only the speed and density of the memory module could be stored because of the limited space for pins.

<div class="mw-heading mw-heading3"><h3 id="SDR_SDRAM">SDR SDRAM</h3></div>

The first SPD specification was issued by JEDEC and tightened up by Intel as part of its <a href="PC100" class="mw-redirect" title="PC100">PC100</a> memory specification introduced in 1998.<a href="#cite_note-4">[4]</a><a href="#cite_note-5">[5]</a><a href="#cite_note-6">[6]</a> Most values specified are in <a href="Binary-coded_decimal" title="Binary-coded decimal">binary-coded decimal</a> form. The most significant <a href="Nibble" title="Nibble">nibble</a> can contain values from 10 to 15, and in some cases extends higher. In such cases, the encodings for 1, 2 and 3 are instead used to encode 16, 17 and 18. A most significant nibble of 0 is reserved to represent "undefined".

The SPD ROM defines up to three DRAM timings, for three CAS latencies specified by set bits in byte 18. First comes the highest CAS latency (fastest clock), then two lower CAS latencies with progressively lower clock speeds.

<caption>SPD contents for SDR SDRAM<a href="#cite_note-spd_pc100-7">[7]</a>

</caption>

<th colspan="2">Byte

</th>

<th colspan="8">Bit

</th>

<th rowspan="2">Notes

</th></tr>

<tr>

<th>(hex.)

</th>

<th>0

</th></tr>

<tr>

<td colspan="8">Number of bytes present</td>

<td>Typically 128

</td></tr>

<tr>

<td colspan="8">log2(size of SPD EEPROM)</td>

<td>Typically 8 (256 bytes)

</td></tr>

<tr>

<td colspan="8">Basic memory type (4: SPD SDRAM)</td>

<td>

</td></tr>

<tr>

<td colspan="4">Bank 2 row address bits (0–15)</td>

<td colspan="4">Bank 1 row address bits (1–15)</td>

<td>Bank 2 is 0 if same as bank 1

</td></tr>

<tr>

<td colspan="4">Bank 2 column address bits (0–15)</td>

<td colspan="4">Bank 1 column address bits (1–15)</td>

<td>Bank 2 is 0 if same as bank 1

</td></tr>

<tr>

<td colspan="8">Number of RAM banks on module (1–255)</td>

<td>Commonly 1 or 2

</td></tr>

<tr>

<td colspan="8">Module data width low byte</td>

<td>Commonly 64, or 72 for ECC DIMMs

</td></tr>

<tr>

<td colspan="8">Module data width high byte</td>

<td>0, unless width ≥ 256 bits

</td></tr>

<tr>

<td colspan="8">Interface voltage level of this assembly (not the same as Vcc supply voltage) (0–4)</td>

<td>Decoded by table lookup

</td></tr>

<tr>

<td colspan="4">Nanoseconds (0–15)</td>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td>Clock cycle time at highest CAS latency

</td></tr>

<tr>

<td colspan="4">Nanoseconds (0–15)</td>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td>SDRAM access time from clock (tAC)

</td></tr>

<tr>

<td colspan="8">DIMM configuration type (0–2): non-ECC, parity, ECC</td>

<td>Table lookup

</td></tr>

<tr>

<td colspan="7">Refresh period (0–5): 64, 256, 128, 32, 16, 8 kHz</td>

<td>Refresh requirements

</td></tr>

<tr>

<td colspan="7">Bank 1 primary SDRAM width (1–127, usually 8)</td>

<td>Width of bank 1 data SDRAM devices. Bank 2 may be same width, or 2× width if bit 7 is set.

</td></tr>

<tr>

<td colspan="7">Bank 1 ECC SDRAM width (0–127)</td>

<td>Width of bank 1 ECC/parity SDRAM devices. Bank 2 may be same width, or 2× width if bit 7 is set.

</td></tr>

<tr>

<td colspan="8">Clock delay for random column reads</td>

<td>Typically 1

</td></tr>

<tr>

<td>Burst lengths supported (bitmap)

</td></tr>

<tr>

<td colspan="8">Banks per SDRAM device (1–255)</td>

<td>Typically 2 or 4

</td></tr>

<tr>

<td>CAS latencies supported (bitmap)

</td></tr>

<tr>

<td>CS latencies supported (bitmap)

</td></tr>

<tr>

<td>WE latencies supported (bitmap)

</td></tr>

<tr>

<td>Redundant</td>

<td>Diff. clock</td>

<td>Registered data</td>

<td>Buffered data</td>

<td>Registered addr.</td>

<td>Buffered addr.</td>

<td>Memory module feature bitmap

</td></tr>

<tr>

<td>Upper Vcc (supply voltage) tolerance</td>

<td>Lower Vcc (supply voltage) tolerance</td>

<td>Write/1 read burst</td>

<td>Precharge all</td>

<td>Auto-precharge</td>

<td>Early RAS precharge</td>

<td>Memory chip feature support bitmap

</td></tr>

<tr>

<td colspan="4">Nanoseconds (4–18)</td>

<td colspan="4">Tenths of nanoseconds (0–9: 0.0–0.9)</td>

<td>Clock cycle time at medium CAS latency

</td></tr>

<tr>

<td colspan="4">Nanoseconds (4–18)</td>

<td colspan="4">Tenths of nanoseconds (0–9: 0.0–0.9)</td>

<td>Data access time from clock (tAC)

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Clock cycle time at short CAS latency.

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Data access time from clock (tAC)

</td></tr>

<tr>

<td colspan="8">Nanoseconds (1–255)</td>

<td>Minimum row precharge time (tRP)

</td></tr>

<tr>

<td colspan="8">Nanoseconds (1–255)</td>

<td>Minimum row active–row active delay (tRRD)

</td></tr>

<tr>

<td colspan="8">Nanoseconds (1–255)</td>

<td>Minimum RAS to CAS delay (tRCD)

</td></tr>

<tr>

<td colspan="8">Nanoseconds (1–255)</td>

<td>Minimum active to precharge time (tRAS)

</td></tr>

<tr>

<td>Module bank density (bitmap). Two bits set if different size banks.

</td></tr>

<tr>

<td colspan="3">Nanoseconds (0–7)</td>

<td colspan="4">Tenths of nanoseconds (0–9: 0.0–0.9)</td>

<td>Address/command setup time from clock

</td></tr>

<tr>

<td colspan="3">Nanoseconds (0–7)</td>

<td colspan="4">Tenths of nanoseconds (0–9: 0.0–0.9)</td>

<td>Address/command hold time after clock

</td></tr>

<tr>

<td colspan="3">Nanoseconds (0–7)</td>

<td colspan="4">Tenths of nanoseconds (0–9: 0.0–0.9)</td>

<td>Data input setup time from clock

</td></tr>

<tr>

<td colspan="3">Nanoseconds (0–7)</td>

<td colspan="4">Tenths of nanoseconds (0–9: 0.0–0.9)</td>

<td>Data input hold time after clock

</td></tr>

<tr>

<td>0x24–0x3d

</td>

<td colspan="8" data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved

</td>

<td>For future standardization

</td></tr>

<tr>

<td colspan="4">Major revision (0–9)</td>

<td colspan="4">Minor revision (0–9)</td>

<td>SPD revision level; e.g., 1.2

</td></tr>

<tr>

<td colspan="8">Checksum</td>

<td>Sum of bytes 0–62, not then negated

</td></tr>

<tr>

<td colspan="8">Manufacturer JEDEC id.</td>

<td>Stored little-endian, trailing zero-padded

</td></tr>

<tr>

<td colspan="8">Module manufacturing location</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td colspan="8">Module part number</td>

<td>ASCII, space-padded

</td></tr>

<tr>

<td colspan="8">Module revision code</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td colspan="4">Tens of years (0–9: 0–90)</td>

<td colspan="4">Years (0–9)</td>

<td rowspan="2">Manufacturing date (YYWW)

</td></tr>

<tr>

<td colspan="4">Tens of weeks (0–5: 0–50)</td>

<td colspan="4">Weeks (0–9)

</td></tr>

<tr>

<td colspan="8">Module serial number</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td colspan="8">Manufacturer-specific data</td>

<td>Could be enhanced performance profile

</td></tr>

<tr>

<td>Intel frequency support

</td></tr>

<tr>

<td>Concurrent AP</td>

<td>Intel feature bitmap

</td></tr></tbody></table>

<div class="mw-heading mw-heading3"><h3 id="DDR_SDRAM">DDR SDRAM</h3></div>

The DDR DIMM SPD format is an extension of the SDR SDRAM format. Mostly, parameter ranges are rescaled to accommodate higher speeds.

<caption>SPD contents for DDR SDRAM<a href="#cite_note-spd_ddr-8">[8]</a>

</caption>

<th colspan="2">Byte

</th>

<th colspan="8">Bit

</th>

<th rowspan="2">Notes

</th></tr>

<tr>

<th>(hex.)

</th>

<th>0

</th></tr>

<tr>

<td colspan="8">Number of bytes written</td>

<td>Typically 128

</td></tr>

<tr>

<td colspan="8">log2(size of SPD EEPROM)</td>

<td>Typically 8 (256 bytes)

</td></tr>

<tr>

<td colspan="8">Basic memory type (7 = DDR SDRAM)</td>

<td>

</td></tr>

<tr>

<td colspan="4">Bank 2 row address bits (0–15)</td>

<td colspan="4">Bank 1 row address bits (1–15)</td>

<td>Bank 2 is 0 if same as bank 1.

</td></tr>

<tr>

<td colspan="4">Bank 2 column address bits (0–15)</td>

<td colspan="4">Bank 1 column address bits (1–15)</td>

<td>Bank 2 is 0 if same as bank 1.

</td></tr>

<tr>

<td colspan="8">Number of RAM banks on module (1–255)</td>

<td>Commonly 1 or 2

</td></tr>

<tr>

<td colspan="8">Module data width low byte</td>

<td>Commonly 64, or 72 for ECC DIMMs

</td></tr>

<tr>

<td colspan="8">Module data width high byte</td>

<td>0, unless width ≥ 256 bits

</td></tr>

<tr>

<td colspan="8">Interface voltage level of this assembly (not the same as Vcc supply voltage) (0–5)</td>

<td>Decoded by table lookup

</td></tr>

<tr>

<td colspan="4">Nanoseconds (0–15)</td>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td>Clock cycle time at highest CAS latency.

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>SDRAM access time from clock (tAC)

</td></tr>

<tr>

<td colspan="8">DIMM configuration type (0–2): non-ECC, parity, ECC</td>

<td>Table lookup

</td></tr>

<tr>

<td colspan="7">Refresh period (0–5): 64, 256, 128, 32, 16, 8 kHz</td>

<td>Refresh requirements

</td></tr>

<tr>

<td colspan="7">Bank 1 primary SDRAM width (1–127)</td>

<td>Width of bank 1 data SDRAM devices. Bank 2 may be same width, or 2× width if bit 7 is set.

</td></tr>

<tr>

<td colspan="7">Bank 1 ECC SDRAM width (0–127)</td>

<td>Width of bank 1 ECC/parity SDRAM devices. Bank 2 may be same width, or 2× width if bit 7 is set.

</td></tr>

<tr>

<td colspan="8">Clock delay for random column reads</td>

<td>Typically 1

</td></tr>

<tr>

<td>Burst lengths supported (bitmap)

</td></tr>

<tr>

<td colspan="8">Banks per SDRAM device (1–255)</td>

<td>Typically 4

</td></tr>

<tr>

<td>CAS latencies supported (bitmap)

</td></tr>

<tr>

<td>CS latencies supported (bitmap)

</td></tr>

<tr>

<td>WE latencies supported (bitmap)

</td></tr>

<tr>

<td>Diff clock</td>

<td>FET switch external enable</td>

<td>FET switch on-board enable</td>

<td>Registered</td>

<td>Buffered</td>

<td>Memory module feature bitmap

</td></tr>

<tr>

<td>Concurrent auto precharge</td>

<td>Upper Vcc (supply voltage) tolerance</td>

<td>Lower Vcc (supply voltage) tolerance</td>

<td>Includes weak driver</td>

<td>Memory chip feature bitmap

</td></tr>

<tr>

<td colspan="4">Nanoseconds (0–15)</td>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td>Clock cycle time at medium CAS latency.

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Data access time from clock (tAC)

</td></tr>

<tr>

<td colspan="4">Nanoseconds (0–15)</td>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td>Clock cycle time at short CAS latency.

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Data access time from clock (tAC)

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Minimum row precharge time (tRP)

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Minimum row active–row active delay (tRRD)

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Minimum RAS to CAS delay (tRCD)

</td></tr>

<tr>

<td colspan="8">Nanoseconds (1–255)</td>

<td>Minimum active to precharge time (tRAS)

</td></tr>

<tr>

<td>Module bank density (bitmap). Two bits set if different size banks.

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Address/command setup time from clock

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Address/command hold time after clock

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Data input setup time from clock

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Data input hold time after clock

</td></tr>

<tr>

<td>36–40

</td>

</td>

<td>Superset information

</td></tr>

<tr>

<td colspan="8">Nanoseconds (1–255)</td>

<td>Minimum active to active/refresh time (tRC)

</td></tr>

<tr>

<td colspan="8">Nanoseconds (1–255)</td>

<td>Minimum refresh to active/refresh time (tRFC)

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63, or 255: no maximum)</td>

<td>Maximum clock cycle time (tCK max.)

</td></tr>

<tr>

<td colspan="8">Hundredths of nanoseconds (0.01–2.55)</td>

<td>Maximum skew, DQS to any DQ. (tDQSQ max.)

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–1.2)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Read data hold skew factor (tQHS)

</td></tr>

<tr>

<td>0x2e

</td>

<td>For future standardization

</td></tr>

<tr>

<td colspan="2">Height</td>

<td>Height of DIMM module, table lookup

</td></tr>

<tr>

<td>0x30–0x3d

</td>

<td>For future standardization

</td></tr>

<tr>

<td colspan="4">Major revision (0–9)</td>

<td colspan="4">Minor revision (0–9)</td>

<td>SPD revision level, 0.0 or 1.0

</td></tr>

<tr>

<td colspan="8">Checksum</td>

<td>Sum of bytes 0–62, not then negated

</td></tr>

<tr>

<td colspan="8">Manufacturer JEDEC id.</td>

<td>Stored little-endian, trailing zero-padded

</td></tr>

<tr>

<td colspan="8">Module manufacturing location</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td colspan="8">Module part number</td>

<td>ASCII, space-padded

</td></tr>

<tr>

<td colspan="8">Module revision code</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td colspan="4">Tens of years (0–90)</td>

<td colspan="4">Years (0–9)</td>

<td rowspan="2">Manufacturing date (YYWW)

</td></tr>

<tr>

<td colspan="4">Tens of weeks (0–50)</td>

<td colspan="4">Weeks (0–9)

</td></tr>

<tr>

<td colspan="8">Module serial number</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td colspan="8">Manufacturer-specific data</td>

<td>Could be enhanced performance profile

</td></tr></tbody></table>

<div class="mw-heading mw-heading3"><h3 id="DDR2_SDRAM">DDR2 SDRAM</h3></div>

The DDR2 SPD standard makes a number of changes, but is roughly similar to the above. One notable deletion is the confusing and little-used support for DIMMs with two ranks of different sizes.

For cycle time fields (bytes 9, 23, 25 and 49), which are encoded in <a href="Binary-coded_decimal" title="Binary-coded decimal">BCD</a>, some additional encodings are defined for the tenths digit to represent some common timings exactly:

<caption>DDR2 BCD extensions

</caption>

<th>Binary</th>

<th>Significance

</th></tr>

<tr>

/* start https://en.wikipedia.org/ */

.mw-parser-output .frac{white-space:nowrap}.mw-parser-output .frac .num,.mw-parser-output .frac .den{font-size:80%;line-height:0;vertical-align:super}.mw-parser-output .frac .den{vertical-align:sub}.mw-parser-output .sr-only{border:0;clip:rect(0,0,0,0);clip-path:polygon(0px 0px,0px 0px,0px 0px);height:1px;margin:-1px;overflow:hidden;padding:0;position:absolute;width:1px}

/* end https://en.wikipedia.org/ */

</style>1⁄4)

</td></tr>

<tr>

<td>0.33 (1⁄3)

</td></tr>

<tr>

<td>0.66 (2⁄3)

</td></tr>

<tr>

<td>0.75 (3⁄4)

</td></tr>

<tr>

<td>0.875 (7⁄8, Nvidia XMP extension)

</td></tr>

<tr>

<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved

</td></tr></tbody></table>

<caption>SPD contents for DDR2 SDRAM<a href="#cite_note-spd_ddr2-9">[9]</a>

</caption>

<th colspan="2">Byte

</th>

<th colspan="8">Bit

</th>

<th rowspan="2">Notes

</th></tr>

<tr>

<th>0

</th></tr>

<tr>

<td colspan="8">Number of bytes written</td>

<td>Typically 128

</td></tr>

<tr>

<td colspan="8">log2(size of SPD EEPROM)</td>

<td>Typically 8 (256 bytes)

</td></tr>

<tr>

<td colspan="8">Basic memory type (8 = DDR2 SDRAM)</td>

<td>

</td></tr>

<tr>

<td colspan="4" data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved</td>

<td colspan="4">Row address bits (1–15)</td>

<td>

</td></tr>

<tr>

<td colspan="4">Column address bits (1–15)</td>

<td>

</td></tr>

<tr>

<td colspan="3">Vertical height</td>

<td>Stack?</td>

<td colspan="3">Ranks−1 (1–8)</td>

<td>Commonly 0 or 1, meaning 1 or 2

</td></tr>

<tr>

<td colspan="8">Module data width</td>

<td>Commonly 64, or 72 for ECC DIMMs

</td></tr>

<tr>

<td>

</td></tr>

<tr>

<td colspan="8">Interface voltage level of this assembly (not the same as Vcc supply voltage) (0–5)</td>

<td>Decoded by table lookup. Commonly 5 = SSTL 1.8 V

</td></tr>

<tr>

<td colspan="4">Nanoseconds (0–15)</td>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td>Clock cycle time at highest CAS latency.

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>SDRAM access time from clock (tAC)

</td></tr>

<tr>

<td colspan="8">DIMM configuration type (0–2): non-ECC, parity, ECC</td>

<td>Table lookup

</td></tr>

<tr>

<td colspan="7">Refresh period (0–5): 64, 256, 128, 32, 16, 8 kHz</td>

<td>Refresh requirements

</td></tr>

<tr>

<td colspan="8">Primary SDRAM width (1–255)</td>

<td>Commonly 8 (module built from ×8 parts) or 16

</td></tr>

<tr>

<td colspan="8">ECC SDRAM width (0–255)</td>

<td>Width of bank ECC/parity SDRAM devices. Commonly 0 or 8.

</td></tr>

<tr>

<td>

</td></tr>

<tr>

<td>Burst lengths supported (bitmap)

</td></tr>

<tr>

<td colspan="8">Banks per SDRAM device (1–255)</td>

<td>Typically 4 or 8

</td></tr>

<tr>

<td>CAS latencies supported (bitmap)

</td></tr>

<tr>

<td>

</td></tr>

<tr>

<td>Mini-UDIMM</td>

<td>Mini-RDIMM</td>

<td>Micro-DIMM</td>

<td>UDIMM</td>

<td>RDIMM</td>

<td>DIMM type of this assembly (bitmap)

</td></tr>

<tr>

<td>Module is analysis probe</td>

<td>FET switch external enable</td>

<td>Memory module feature bitmap

</td></tr>

<tr>

<td>Includes weak driver</td>

<td>Memory chip feature bitmap

</td></tr>

<tr>

<td colspan="4">Nanoseconds (0–15)</td>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td>Clock cycle time at medium CAS latency.

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Data access time from clock (tAC)

</td></tr>

<tr>

<td colspan="4">Nanoseconds (0–15)</td>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td>Clock cycle time at short CAS latency.

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Data access time from clock (tAC)

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Minimum row precharge time (tRP)

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Minimum row active–row active delay (tRRD)

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Minimum RAS to CAS delay (tRCD)

</td></tr>

<tr>

<td colspan="8">Nanoseconds (1–255)</td>

<td>Minimum active to precharge time (tRAS)

</td></tr>

<tr>

<td>Size of each rank (bitmap).

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–1.2)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Address/command setup time from clock

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–1.2)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Address/command hold time after clock

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Data input setup time from strobe

</td></tr>

<tr>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td colspan="4">Hundredths of nanoseconds (0.00–0.09)</td>

<td>Data input hold time after strobe

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Minimum write recovery time (tWR)

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Internal write to read command delay (tWTR)

</td></tr>

<tr>

<td colspan="6">Nanoseconds (1–63)</td>

<td>Internal read to precharge command delay (tRTP)

</td></tr>

<tr>

<td>Reserved for "memory analysis probe characteristics"

</td></tr>

<tr>

<td colspan="3">tRC fractional ns (0–5): 0, 0.25, 0.33, 0.5, 0.66, 0.75</td>

<td colspan="3">tRFC fractional ns (0–5): 0, 0.25, 0.33, 0.5, 0.66, 0.75</td>

<td>Extension of bytes 41 and 42.

</td></tr>

<tr>

<td colspan="8">Nanoseconds (1–255)</td>

<td>Minimum active to active/refresh time (tRC)

</td></tr>

<tr>

<td colspan="8">Nanoseconds (1–255)</td>

<td>Minimum refresh to active/refresh time (tRFC)

</td></tr>

<tr>

<td colspan="4">Nanoseconds (0–15)</td>

<td colspan="4">Tenths of nanoseconds (0.0–0.9)</td>

<td>Maximum clock cycle time (tCK max)

</td></tr>

<tr>

<td colspan="8">Hundredths of nanoseconds (0.01–2.55)</td>

<td>Maximum skew, DQS to any DQ. (tDQSQ max)

</td></tr>

<tr>

<td colspan="8">Hundredths of nanoseconds (0.01–2.55)</td>

<td>Read data hold skew factor (tQHS)

</td></tr>

<tr>

<td colspan="8">Microseconds (1–255)</td>

<td>PLL relock time

</td></tr>

<tr>

<td>For future standardization.

</td></tr>

<tr>

<td colspan="4">Major revision (0–9)</td>

<td colspan="4">Minor revision (0.0–0.9)</td>

<td>SPD revision level, usually 1.0

</td></tr>

<tr>

<td colspan="8">Checksum</td>

<td>Sum of bytes 0–62, not negated

</td></tr>

<tr>

<td colspan="8">Manufacturer JEDEC ID</td>

<td>Stored little-endian, trailing zero-pad

</td></tr>

<tr>

<td colspan="8">Module manufacturing location</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td colspan="8">Module part number</td>

<td>ASCII, space-padded (limited to (,-,), A–Z, a–z, 0–9, space)

</td></tr>

<tr>

<td colspan="8">Module revision code</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td colspan="8">Years since 2000 (0–255)</td>

<td rowspan="2">Manufacturing date (YYWW)

</td></tr>

<tr>

<td colspan="8">Weeks (1–52)

</td></tr>

<tr>

<td colspan="8">Module serial number</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td colspan="8">Manufacturer-specific data</td>

<td>Could be enhanced performance profile

</td></tr></tbody></table>

<div class="mw-heading mw-heading3"><h3 id="DDR3_SDRAM">DDR3 SDRAM</h3></div>

The DDR3 SDRAM standard significantly overhauls and simplifies the SPD contents layout. Instead of a number of BCD-encoded nanosecond fields, some "timebase" units are specified to high precision, and various timing parameters are encoded as multiples of that base unit.<a href="#cite_note-10">[10]</a> Further, the practice of specifying different time values depending on the CAS latency has been dropped; now there are just a single set of timing parameters.

Revision 1.1 lets some parameters be expressed as a "medium time base" value plus a (signed, −128 +127) "fine time base" correction. Generally, the medium time base is 1/8 ns (125 ps), and the fine time base is 1, 2.5 or 5 ps. For compatibility with earlier versions that lack the correction, the medium time base number is usually rounded up and the correction is negative. Values that work this way are:

<caption>DDR3 SPD two-part timing parameters

</caption>

<th>Value

</th></tr>

<tr>

<td>tCKmin, minimum clock period

</td></tr>

<tr>

<td>tAAmin, minimum CAS latency time

</td></tr>

<tr>

<td>tRCDmin, minimum RAS# to CAS# delay

</td></tr>

<tr>

<td>tRPmin, minimum row precharge delay

</td></tr>

<tr>

<td>tRCmin, minimum active to active/precharge delay

</td></tr></tbody></table>

<caption>SPD contents for DDR3 SDRAM<a href="#cite_note-spd_ddr3_docs-11">[11]</a><a href="#cite_note-12">[12]</a>

</caption>

<th colspan="2">Byte

</th>

<th colspan="8">Bit

</th>

<th rowspan="2">Notes

</th></tr>

<tr>

<th>0

</th></tr>

<tr>

<td>Exclude serial from CRC</td>

<td colspan="3">SPD bytes total (undef/256)</td>

<td colspan="4">SPD bytes used (undef/128/176/256)</td>

<td>

</td></tr>

<tr>

<td colspan="4">SPD major revision</td>

<td colspan="4">SPD minor revision</td>

<td>1.0, 1.1, 1.2 or 1.3

</td></tr>

<tr>

<td colspan="8">Basic memory type (11 = DDR3 SDRAM)</td>

<td>Type of RAM chips

</td></tr>

<tr>

<td colspan="4">Module type</td>

<td>Type of module; e.g., 2 = Unbuffered DIMM, 3 = SO-DIMM, 11=LRDIMM

</td></tr>

<tr>

<td colspan="3">Bank address bits−3</td>

<td>Zero means 8 banks, 256 Mibit.

</td></tr>

<tr>

<td colspan="3">Row address bits−12</td>

<td colspan="3">Column address bits−9</td>

<td>

</td></tr>

<tr>

<td colspan="5" data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved</td>

<td>Modules voltages supported. 1.5 V is default.

</td></tr>

<tr>

<td colspan="3">ranks−1</td>

<td>Module organization

</td></tr>

<tr>

<td>0x03 for 64-bit, non-ECC DIMM.

</td></tr>

<tr>

<td colspan="4">Dividend, picoseconds (1–15)</td>

<td colspan="4">Divisor, picoseconds (1–15)</td>

<td>Fine Time Base, dividend/divisor

</td></tr>

<tr>

<td colspan="8">Dividend, nanoseconds (1–255)</td>

<td rowspan="2">Medium Time Base, dividend/divisor; commonly 1/8

</td></tr>

<tr>

<td colspan="8">Divisor, nanoseconds (1–255)

</td></tr>

<tr>

<td colspan="8">Minimum cycle time tCKmin</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td>

</td></tr>

<tr>

<td rowspan="2">CAS latencies supported (bitmap)

</td></tr>

<tr>

<td>12

</td></tr>

<tr>

<td colspan="8">Minimum CAS latency time, tAAmin</td>

<td>In multiples of MTB; e.g., 80/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum write recovery time, tWRmin</td>

<td>In multiples of MTB; e.g., 120/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum RAS to CAS delay time, tRCDmin</td>

<td>In multiples of MTB; e.g., 100/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum row to row active delay time, tRRDmin</td>

<td>In multiples of MTB; e.g., 60/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum row precharge time, tRPmin</td>

<td>In multiples of MTB; e.g., 100/8 ns.

</td></tr>

<tr>

<td colspan="4">tRCmin, bits 11:8</td>

<td colspan="4">tRASmin, bits 11:8</td>

<td>Upper 4 bits of bytes 23 and 22

</td></tr>

<tr>

<td colspan="8">Minimum active to time, tRASmin, bits 7:0</td>

<td>In multiples of MTB; e.g., 280/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum active to active/refresh, tRCmin, bits 7:0</td>

<td>In multiples of MTB; e.g., 396/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum refresh recovery delay, tRFCmin, bits 7:0</td>

<td rowspan="2">In multiples of MTB; e.g., 1280/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum refresh recovery delay, tRFCmin, bits 15:8

</td></tr>

<tr>

<td colspan="8">Minimum internal write to read delay, tWTRmin</td>

<td>In multiples of MTB; e.g., 60/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum internal read to precharge delay, tRTPmin</td>

<td>In multiples of MTB; e.g., 60/8 ns.

</td></tr>

<tr>

<td colspan="4">tFAWmin, bits 11:8</td>

<td rowspan="2">In multiples of MTB; e.g., 240/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum four activate window delay tFAWmin, bits 7:0

</td></tr>

<tr>

<td>SDRAM optional features support bitmap

</td></tr>

<tr>

<td>SDRAM thermal and refresh options

</td></tr>

<tr>

<td>Present</td>

<td colspan="7">Accuracy (TBD; currently 0 = undefined)</td>

<td>DIMM thermal sensor present?

</td></tr>

<tr>

<td>Nonstd.</td>

<td colspan="3">Die count</td>

<td colspan="2">Signal load</td>

<td>Nonstandard SDRAM device type (e.g., stacked die)

</td></tr>

<tr>

<td colspan="8">tCKmin correction (new for 1.1)</td>

<td>Signed multiple of FTB, added to byte 12

</td></tr>

<tr>

<td colspan="8">tAAmin correction (new for 1.1)</td>

<td>Signed multiple of FTB, added to byte 16

</td></tr>

<tr>

<td colspan="8">tRCDmin correction (new for 1.1)</td>

<td>Signed multiple of FTB, added to byte 18

</td></tr>

<tr>

<td colspan="8">tRPmin correction (new for 1.1)</td>

<td>Signed multiple of FTB, added to byte 20

</td></tr>

<tr>

<td colspan="8">tRCmin correction (new for 1.1)</td>

<td>Signed multiple of FTB, added to byte 23

</td></tr>

<tr>

<td>For future standardization.

</td></tr>

<tr>

<td colspan="2">Vendor specific</td>

<td colspan="4">Maximum Activate Count (MAC) (untested/700k/600k/.../200k/reserved/∞)</td>

<td>For <a href="Row_hammer" title="Row hammer">row hammer</a> mitigation

</td></tr>

<tr>

<td>For future standardization.

</td></tr>

<tr>

<td colspan="5">Module height, mm (1–31, >45)</td>

<td>Module nominal height

</td></tr>

<tr>

<td colspan="4">Back thickness, mm (1–16)</td>

<td colspan="4">Front thickness, mm (1–16)</td>

<td>Module thickness, value = ceil(mm) − 1

</td></tr>

<tr>

<td>Design</td>

<td colspan="2">Revision</td>

<td colspan="5">JEDEC design number</td>

<td>JEDEC reference design used (11111=none)

</td></tr>

<tr>

<td colspan="8">Module-specific section</td>

<td>Differs between registered/unbuffered

</td></tr>

<tr>

<td colspan="8">Module manufacturer ID, lsbyte</td>

<td rowspan="2">Assigned by JEP-106

</td></tr>

<tr>

<td colspan="8">Module manufacturer ID, msbyte

</td></tr>

<tr>

<td colspan="8">Module manufacturing location</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td colspan="4">Tens of years</td>

<td colspan="4">Years</td>

<td>Manufacturing year (BCD)

</td></tr>

<tr>

<td colspan="4">Tens of weeks</td>

<td colspan="4">Weeks</td>

<td>Manufacturing week (BCD)

</td></tr>

<tr>

<td colspan="8">Module serial number</td>

<td>Vendor-specific code

</td></tr>

<tr>

<td>Includes bytes 0–116 or 0–125; see byte 0 bit 7

</td></tr>

<tr>

<td colspan="8">Module part number</td>

<td>ASCII subset, space-padded

</td></tr>

<tr>

<td colspan="8">Module revision code</td>

<td>Vendor-defined

</td></tr>

<tr>

<td colspan="8">DRAM manufacturer ID</td>

<td>As distinct from module manufacturer

</td></tr>

<tr>

<td colspan="8">Manufacturer-specific data

</td></tr>

<tr>

<td colspan="8">Available for customer use

</td></tr></tbody></table>

The memory capacity of a module can be computed from bytes 4, 7 and 8. The module width (byte 8) divided by the number of bits per chip (byte 7) gives the number of chips per rank. That can then be multiplied by the per-chip capacity (byte 4) and the number of ranks of chips on the module (usually 1 or 2, from byte 7).

<div class="mw-heading mw-heading3"><h3 id="DDR4_SDRAM">DDR4 SDRAM</h3></div>

The DDR4 SDRAM "Annex L" standard for SPD changes the EEPROM module used. Instead of the old AT24C02-compatible 256-byte EEPROMs, JEDEC now defines a new nonstandard EE1004 type with two pages at the SMBus level each with 256 bytes. The new memory still uses the old 0x50–0x57 addresses, but two additional address at 0x36 (SPA0) and 0x37 (SPA1) are now used to receive commands to select the currently-active page for the bus, a form of <a href="Bank_switching" title="Bank switching">bank switching</a>.<a href="#cite_note-13">[13]</a> Internally each logical page is further divided into two physical blocks of 128 bytes each, totaling four blocks and 512 bytes.<a href="#cite_note-annex_l-14">[14]</a> Other semantics for "special" address ranges remain the same, although write protection is now addressed by blocks and a high voltage at SA0 is now required to change its status.<a href="#cite_note-TSE2004-15">[15]</a>

Annex L defines a few different layouts that can be plugged into a 512-byte (of which a maximum of 320 bytes are defined) template, depending on the type of the memory module. The bit definitions are similar to DDR3.<a href="#cite_note-annex_l-14">[14]</a>

<caption>SPD contents for DDR4 SDRAM<a href="#cite_note-spd_ddr4_docs-16">[16]</a>

</caption>

<th colspan="2">Byte

</th>

<th colspan="8">Bit

</th>

<th rowspan="2">Notes

</th></tr>

<tr>

<th>0

</th></tr>

<tr>

<td colspan="8">SPD bytes used

</td></tr>

<tr>

<td colspan="8">SPD revision n</td>

<td>Typically 0x10, 0x11, 0x12

</td></tr>

<tr>

<td colspan="8">Basic memory type (12 = DDR4 SDRAM)</td>

<td>Type of RAM chips

</td></tr>

<tr>

<td colspan="4">Module type</td>

<td>Type of module; e.g., 2 = Unbuffered DIMM, 3 = SO-DIMM, 11=LRDIMM

</td></tr>

<tr>

<td colspan="2">Bank group bits</td>

<td colspan="2">Bank address bits−2</td>

<td colspan="4">Total SDRAM capacity per die in megabits</td>

<td>Zero means no bank groups, 4 banks, 256 Mibit.

</td></tr>

<tr>

<td colspan="3">Row address bits−12</td>

<td colspan="3">Column address bits−9</td>

<td>

</td></tr>

<tr>

<td>Primary SDRAM package type</td>

<td colspan="3">Die count</td>

<td colspan="2">Signal loading

</td></tr>

<tr>

<td colspan="2">Maximum activate window (tMAW)</td>

<td colspan="4">Maximum activate count (MAC)</td>

<td>SDRAM optional features

</td></tr>

<tr>

<td>SDRAM thermal and refresh options

</td></tr>

<tr>

<td colspan="2">Post package repair (PPR)</td>

<td>Other SDRAM optional features

</td></tr>

<tr>

<td>SDRAM package type</td>

<td colspan="3">Die count−1</td>

<td colspan="2">DRAM density ratio</td>

<td colspan="2">Signal loading</td>

<td>Secondary SDRAM package type

</td></tr>

<tr>

<td colspan="6" data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved</td>

<td>Endurant flag</td>

<td>Operable flag</td>

<td>Module nominal voltage, VDD

</td></tr>

<tr>

<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved</td>

<td colspan="3">Package ranks per DIMM−1</td>

<td colspan="3">SDRAM device width</td>

<td>Module organization

</td></tr>

<tr>

<td colspan="2">Bus width extension</td>

<td colspan="3">Primary bus width</td>

<td>Module memory bus width in bits

</td></tr>

<tr>

<td>Thermal sensor</td>

<td colspan="7" data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved</td>

<td>Module thermal sensor

</td></tr>

<tr>

<td colspan="4">Extended base module type

</td></tr>

<tr>

</td></tr>

<tr>

<td colspan="2">Medium timebase (MTB)</td>

<td colspan="2">Fine timebase (FTB)</td>

<td>Measured in ps.

</td></tr>

<tr>

<td colspan="8">Minimum SDRAM cycle time, tCKAVGmin</td>

<td>In multiples of MTB; e.g., 100/8 ns.

</td></tr>

<tr>

<td colspan="8">Maximum SDRAM cycle time, tCKAVGmax</td>

<td>In multiples of MTB; e.g., 60/8 ns.

</td></tr>

<tr>

<td>CAS latencies supported bit-mask

</td></tr>

<tr>

<td>CAS latencies supported bit-mask

</td></tr>

<tr>

<td>CAS latencies supported bit-mask

</td></tr>

<tr>

<td>Low CL range</td>

<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved</td>

<td>CAS latencies supported bit-mask

</td></tr>

<tr>

<td colspan="8">Minimum CAS latency time, tAAmin</td>

<td>In multiples of MTB; e.g., 1280/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum RAS to CAS delay time, tRCDmin</td>

<td>In multiples of MTB; e.g., 60/8 ns.

</td></tr>

<tr>

<td colspan="8">Minimum row precharge delay time, tRPmin</td>

<td>In multiples of MTB; e.g., 60/8 ns.

</td></tr>

<tr>

<td colspan="8">Upper nibbles for tRASmin and tRCmin

</td></tr>

<tr>

<td colspan="8">Minimum active to precharge delay time, tRASmin least significant byte</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum active to active/refresh delay time, tRCmin least significant byte</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum refresh recovery delay time, tRFC1min least significant byte</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum refresh recovery delay time, tRFC1min most significant byte</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum refresh recovery delay time, tRFC2min least significant byte</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum refresh recovery delay time, tRFC2min most significant byte</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum refresh recovery delay time, tRFC4min least significant byte</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum refresh recovery delay time, tRFC4min most significant byte</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="4">tFAWmin most significant nibble

</td></tr>

<tr>

<td colspan="8">Minimum four activate window delay time, tFAWmin least significant byte</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum activate to activate delay time, tRRD_Smin, different bank group</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum activate to activate delay time, tRRD_Lmin, same bank group</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum CAS to CAS delay time, tCCD_Lmin, same bank group</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Upper nibble for tWRmin

</td></tr>

<tr>

<td colspan="8">Minimum write recovery time, tWRmin</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Upper nibbles for tWTRmin

</td></tr>

<tr>

<td colspan="8">Minimum write to read time, tWTR_Smin, different bank group</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td colspan="8">Minimum write to read time, tWTR_Lmin, same bank group</td>

<td>In multiples of MTB

</td></tr>

<tr>

<td>Base configuration section

</td></tr>

<tr>

<td colspan="8">Connector to SDRAM bit mapping

</td></tr>

<tr>

<td>Base configuration section

</td></tr>

<tr>

<td colspan="8">Fine offset for minimum CAS to CAS delay time, tCCD_Lmin, same bank</td>

<td>Two's complement multiplier for FTB units

</td></tr>

<tr>

<td colspan="8">Fine offset for minimum activate to activate delay time, tRRD_Lmin, same bank group</td>

<td>Two's complement multiplier for FTB units

</td></tr>

<tr>

<td colspan="8">Fine offset for minimum activate to activate delay time, tRRD_Smin, different bank group</td>

<td>Two's complement multiplier for FTB units

</td></tr>

<tr>

<td colspan="8">Fine offset for minimum active to active/refresh delay time, tRCmin</td>

<td>Two's complement multiplier for FTB units

</td></tr>

<tr>

<td colspan="8">Fine offset for minimum row precharge delay time, tRPmin</td>

<td>Two's complement multiplier for FTB units

</td></tr>

<tr>

<td colspan="8">Fine offset for minimum RAS to CAS delay time, tRCDmin</td>

<td>Two's complement multiplier for FTB units

</td></tr>

<tr>

<td colspan="8">Fine offset for minimum CAS latency time, tAAmin</td>

<td>Two's complement multiplier for FTB units

</td></tr>

<tr>

<td colspan="8">Fine offset for SDRAM maximum cycle time, tCKAVGmax</td>

<td>Two's complement multiplier for FTB units

</td></tr>

<tr>

<td colspan="8">Fine offset for SDRAM minimum cycle time, tCKAVGmin</td>

<td>Two's complement multiplier for FTB units

</td></tr>

<tr>

<td colspan="8">Cyclic rendundancy code (CRC) for base config section, least significant byte</td>

<td>CRC16 algorithm

</td></tr>

<tr>

<td colspan="8">Cyclic rendundancy code (CRC) for base config section, most significant byte</td>

<td>CRC16 algorithm

</td></tr>

<tr>

<td colspan="8">Module-specific section</td>

<td>Dependent upon memory module family (UDIMM, RDIMM, LRDIMM)

</td></tr>

<tr>

<td colspan="8">Hybrid memory architecture specific parameters

</td></tr>

<tr>

<td colspan="8">Extended function parameter block

</td></tr>

<tr>

<td colspan="8">Module manufacturer</td>

<td>See JEP-106

</td></tr>

<tr>

<td colspan="8">Module manufacturing location</td>

<td>Manufacturer-defined manufacturing location code

</td></tr>

<tr>

<td colspan="8">Module manufacturing year</td>

<td>Represented in Binary Coded Decimal (BCD)

</td></tr>

<tr>

<td colspan="8">Module manufacturing week</td>

<td>Represented in Binary Coded Decimal (BCD)

</td></tr>

<tr>

<td colspan="8">Module serial number</td>

<td>Manufacturer-defined format for a unique serial number across part numbers

</td></tr>

<tr>

<td colspan="8">Module part number</td>

<td>ASCII part number, unused digits should be set to 0x20

</td></tr>

<tr>

<td colspan="8">Module revision code</td>

<td>Manufacturer-defined revision code

</td></tr>

<tr>

<td colspan="8">DRAM manufacturer ID code</td>

<td>See JEP-106

</td></tr>

<tr>

<td colspan="8">DRAM stepping</td>

<td>Manufacturer-defined stepping or 0xFF if not used

</td></tr>

<tr>

<td colspan="8">Manufacturer's specific data

</td></tr>

<tr>

</td></tr></tbody></table>

<div class="mw-heading mw-heading3"><h3 id="DDR5_SDRAM">DDR5 SDRAM</h3></div>

Preliminary table for DDR5, based on JESD400-5 specification.<a href="#cite_note-17">[17]</a>

DDR5 expands the SPD table to 1024-byte. SPD of DDR5 is using the <a href="I3C_(bus)" title="I3C (bus)">I3C</a> bus.

<caption>SPD contents for DDR5 SDRAM

</caption>

<th colspan="2">Byte

</th>

<th colspan="8">Bit

</th>

<th rowspan="2">Notes

</th></tr>

<tr>

<th>0

</th></tr>

<tr>

<td colspan="8">Number of bytes in SPD device</td>

<td>

</td></tr>

<tr>

<td colspan="8">SPD revision for base configuration parameters</td>

<td>

</td></tr>

<tr>

<td colspan="8">Key byte / host bus command protocol type</td>

<td>

</td></tr>

<tr>

<td colspan="8">Key byte / module type</td>

<td>

</td></tr>

<tr>

<td colspan="8">First SDRAM density and package</td>

<td>

</td></tr>

<tr>

<td colspan="8">First SDRAM addressing</td>

<td>

</td></tr>

<tr>

<td colspan="8">First SDRAM I/O width</td>

<td>

</td></tr>

<tr>

<td colspan="8">First SDRAM bank groups & banks per bank group</td>

<td>

</td></tr>

<tr>

<td colspan="8">Second SDRAM density and package</td>

<td>

</td></tr>

<tr>

<td colspan="8">Second SDRAM addressing</td>

<td>

</td></tr>

<tr>

<td colspan="8">Second SDRAM I/O width</td>

<td>

</td></tr>

<tr>

<td colspan="8">Second SDRAM bank groups & banks per bank group</td>

<td>

</td></tr>

<tr>

<td colspan="8">SDRAM optional features</td>

<td>

</td></tr>

<tr>

<td colspan="8">Thermal and refresh options</td>

<td>

</td></tr>

<tr>

<td>

</td></tr>

<tr>

<td>

</td></tr>

<tr>

<td colspan="8">SDRAM nominal voltage, VDD</td>

<td>

</td></tr>

</tbody></table>

<div class="mw-heading mw-heading2"><h2 id="Extensions">Extensions</h2></div>

The JEDEC standard only specifies some of the SPD bytes. The truly critical data fits into the first 64 bytes,<a href="#cite_note-spd_ddr-8">[8]</a><a href="#cite_note-spd_ddr2-9">[9]</a><a href="#cite_note-spd_ddr3-18">[18]</a><a href="#cite_note-spd_base-19">[19]</a><a href="#cite_note-spd_sdr-20">[20]</a> while some of the remainder is earmarked for manufacturer identification. However, a 256-byte EEPROM is generally provided. A number of uses have been made of the remaining space.

Memory generally comes with conservative timing recommendations in the SPD ROM, to ensure basic functionality on all systems. Enthusiasts often spend considerable time manually adjusting the memory timings for higher speed. Enabling special configurations such as Intel XMP or AMD EXPO often requires additional testing to ensure system stability<a href="#cite_note-21">[21]</a> and may void CPU warranty if used out of the manufacturer’s published specifications.<a href="#cite_note-22">[22]</a><a href="#cite_note-23">[23]</a><a href="#cite_note-24">[24]</a>

<div class="mw-heading mw-heading3"><h3 id="Enhanced_Performance_Profiles_(EPP)">Enhanced Performance Profiles (EPP)</h3></div>

Enhanced Performance Profiles is an extension of SPD, developed by <a href="Nvidia" title="Nvidia">Nvidia</a> and <a href="Corsair_Gaming" title="Corsair Gaming">Corsair</a>, which includes additional information for higher-performance operation of <a href="DDR2_SDRAM" title="DDR2 SDRAM">DDR2 SDRAM</a>, including supply voltages and command timing information not included in the JEDEC SPD spec. The EPP information is stored in the same EEPROM, but in bytes 99–127, which are unused by standard DDR2 SPD.<a href="#cite_note-25">[25]</a>

<caption>EPP SPD ROM usage

</caption>

<th>Bytes</th>

<th>Full profiles</th>

<th>Abbreviated profiles

</th></tr>

<tr>

<td colspan="2">EPP header

</td></tr>

<tr>

<td rowspan="2">Profile FP1</td>

<td>Profile AP1

</td></tr>

<tr>

<td>Profile AP2

</td></tr>

<tr>

<td rowspan="2">Profile FP2</td>

<td>Profile AP3

</td></tr>

<tr>

<td>Profile AP4

</td></tr></tbody></table>

The parameters are particularly designed to fit the memory controller on the <a href="NForce_500" title="NForce 500">nForce 5</a>, <a href="NForce_600" title="NForce 600">nForce 6</a> and <a href="NForce_700" title="NForce 700">nForce 7</a> chipsets. Nvidia encourages support for EPP in the <a href="BIOS" title="BIOS">BIOS</a> for its high-end motherboard chipsets. This is intended to provide "one-click <a href="Overclocking" title="Overclocking">overclocking</a>" to get better performance with minimal effort.

Nvidia's name for EPP memory that has been qualified for performance and stability is "SLI-ready memory".<a href="#cite_note-26">[26]</a> The term "SLI-ready-memory" has caused some confusion, as it has nothing to do with <a href="Scalable_Link_Interface" title="Scalable Link Interface">SLI video</a>. One can use EPP/SLI memory with a single video card (even a non-Nvidia card), and one can run a multi-card SLI video setup without EPP/SLI memory.

An extended version, EPP 2.0, supports DDR3 memory as well.<a href="#cite_note-27">[27]</a>

<div class="mw-heading mw-heading3"><h3 id="Intel_Extreme_Memory_Profile_(XMP)">Intel Extreme Memory Profile (XMP)</h3></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">"Intel XMP" redirects here; not to be confused with <a href="Intel_MPX" title="Intel MPX">Intel MPX</a>.</div>

A similar, <a href="Intel" title="Intel">Intel</a>-developed JEDEC SPD extension was developed for <a href="DDR3_SDRAM" title="DDR3 SDRAM">DDR3 SDRAM</a> DIMMs, later used in <a href="DDR4_SDRAM" title="DDR4 SDRAM">DDR4</a> and <a href="DDR5_SDRAM" title="DDR5 SDRAM">DDR5 SDRAM</a> as well. XMP uses bytes 176–255, which are unallocated by JEDEC, to encode higher-performance memory timings.<a href="#cite_note-28">[28]</a>

Later, AMD developed AMP, an equivalent technology to XMP, for use in its "Radeon Memory" line of memory modules optimized for use in AMD platforms.<a href="#cite_note-29">[29]</a><a href="#cite_note-30">[30]</a> Furthermore, motherboard developers implemented their own technologies to allow their AMD-based motherboards to read XMP profiles: MSI offers A-XMP,<a href="#cite_note-31">[31]</a> ASUS has DOCP (Direct Over Clock Profile), and Gigabyte has EOCP (Extended Over Clock Profile).<a href="#cite_note-32">[32]</a>

<caption>XMP SPD ROM usage<a href="#cite_note-xmp1.1-33">[33]</a>

</caption>

<th>DDR3 Bytes</th>

<th>Use

</th></tr>

<tr>

<td>XMP header

</td></tr>

<tr>

<td>XMP profile 1 ("enthusiast" settings)

</td></tr>

<tr>

<td>XMP profile 2 ("extreme" settings)

</td></tr></tbody></table>

The header contains the following data. Most importantly, it contains a "medium timebase" value MTB, as a rational number of nanoseconds (common values are 1/8, 1/12 and 1/16 ns). Many other later timing values are expressed as an integer number of MTB units.

Also included in the header is the number of DIMMs per memory channel that the profile is designed to support; including more DIMMs may not work well.

<caption>XMP Header bytes<a href="#cite_note-xmp1.1-33">[33]</a>

</caption>

<th>Use

</th></tr>

<tr>

<td>XMP <a href="Magic_number_(programming)" title="Magic number (programming)">magic number</a> byte 1 0x0C

</td></tr>

<tr>

<td>XMP magic number byte 2 0x4A

</td></tr>

<tr>

<td>Profile 1 enabled (if 0, disabled)

</td></tr>

<tr>

<td>Profile 2 enabled

</td></tr>

<tr>

<td>Profile 1 DIMMs per channel (1–4 encoded as 0–3)

</td></tr>

<tr>

<td>Profile 2 DIMMs per channel

</td></tr>

<tr>

<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved

</td></tr>

<tr>

<td>XMP minor version number (x.0 or x.1)

</td></tr>

<tr>

<td>XMP major version number (0.x or 1.x)

</td></tr>

<tr>

<td>Medium timebase dividend for profile 1

</td></tr>

<tr>

<td>Medium timebase divisor for profile 1 (MTB = dividend/divisor ns)

</td></tr>

<tr>

<td>Medium timebase dividend for profile 2 (e.g. 8)

</td></tr>

<tr>

<td>Medium timebase divisor for profile 2 (e.g. 1, giving MTB = 1/8 ns)

</td></tr>

<tr>

<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved

</td></tr></tbody></table>

<caption>XMP profile bytes<a href="#cite_note-xmp1.1-33">[33]</a>

</caption>

<th>Use

</th></tr>

<tr>

<td>Module Vdd voltage twentieths (0.00 or 0.05)

</td></tr>

<tr>

<td>Module Vdd voltage tenths (0.0–0.9)

</td></tr>

<tr>

<td>Module Vdd voltage units (0–2)

</td></tr>

<tr>

<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved

</td></tr>

<tr>

<td>Minimum SDRAM clock period tCKmin (MTB units)

</td></tr>

<tr>

<td>Minimum CAS latency time tAAmin (MTB units)

</td></tr>

<tr>

<td>CAS latencies supported (bitmap, 4–11 encoded as bits 0–7)

</td></tr>

<tr>

<td>CAS latencies supported (bitmap, 12–18 encoded as bits 0–6)

</td></tr>

<tr>

<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved

</td></tr>

<tr>

<td>Minimum CAS write latency time tCWLmin (MTB units)

</td></tr>

<tr>

<td>Minimum row precharge delay time tRPmin (MTB units)

</td></tr>

<tr>

<td>Minimum RAS to CAS delay time tRCDmin (MTB units)

</td></tr>

<tr>

<td>Minimum write recovery time tWRmin (MTB units)

</td></tr>

<tr>

<td>tRASmin upper <a href="Nibble" title="Nibble">nibble</a> (bits 11:8)

</td></tr>

<tr>

<td>tRCmin upper nibble (bits 11:8)

</td></tr>

<tr>

<td>Minimum active to precharge delay time tRASmin bits 7:0 (MTB units)

</td></tr>

<tr>

<td>Minimum active to active/refresh delay time tRCmin bits 7:0 (MTB units)

</td></tr>

<tr>

<td>Maximum average refresh interval tREFI lsbyte (MTB units)

</td></tr>

<tr>

<td>Maximum average refresh interval tREFI msbyte (MTB units)

</td></tr>

<tr>

<td>Minimum refresh recovery delay time tRFCmin lsbyte (MTB units)

</td></tr>

<tr>

<td>Minimum refresh recovery delay time tRFCmin msbyte (MTB units)

</td></tr>

<tr>

<td>Minimum internal read to precharge command delay time tRTPmin (MTB units)

</td></tr>

<tr>

<td>Minimum row active to row active delay time tRRDmin (MTB units)

</td></tr>

<tr>

<td>tFAWmin upper nibble (bits 11:8)

</td></tr>

<tr>

<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved

</td></tr>

<tr>

<td>Minimum four activate window delay time tFAWmin bits 7:0 (MTB units)

</td></tr>

<tr>

<td>Minimum internal write to read command delay time tWTRmin (MTB units)

</td></tr>

<tr>

<td>Write to read command turnaround time adjustment (0–7 clock cycles)

</td></tr>

<tr>

<td>Write to read command turnaround adjustment sign (0=pull-in, 1=push-out)

</td></tr>

<tr>

<td>Read to write command turnaround time adjustment (0–7 clock cycles)

</td></tr>

<tr>

<td>Read to write command turnaround adjustment sign (0=pull-in, 1=push-out)

</td></tr>

<tr>

<td>Back-to-back command turnaround time adjustment (0–7 clock cycles)

</td></tr>

<tr>

<td>Back-to-back turnaround adjustment sign (0=pull-in, 1=push-out)

</td></tr>

<tr>

<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved

</td></tr>

<tr>

<td>System CMD rate mode. 0=JTAG default, otherwise in peculiar units of MTB × tCK/ns. E.g. if MTB is 1/8 ns, then this is in units of 1/8 clock cycle.

</td></tr>

<tr>

<td>SDRAM auto self refresh performance. Standard version 1.1 says documentation is <a href="https://en.wiktionary.org/wiki/TBD" class="extiw external" title="wikt:TBD">TBD</a>.

</td></tr>

<tr>

<td data-sort-value="" style="background: var(--background-color-interactive, #ececec); color: var(--color-base, inherit); vertical-align: middle; text-align: center;" class="table-na">Reserved

</td></tr>

<tr>

<td>Reserved, vendor-specific personality code.

</td></tr></tbody></table>

All data above are for DDR3 (XMP 1.1); DDR4 specs are not yet available.

<div class="mw-heading mw-heading3"><h3 id="AMD_Extended_Profiles_for_Overclocking_(EXPO)">AMD Extended Profiles for Overclocking (EXPO)</h3></div>

AMD's Extended Profiles for Overclocking (EXPO) is a JEDEC SPD extension developed for <a href="DDR5_SDRAM" title="DDR5 SDRAM">DDR5</a> DIMMs to apply a one-click automatic overclocking profile to system memory.<a href="#cite_note-34">[34]</a><a href="#cite_note-JRoachDigitalTrends-35">[35]</a> AMD EXPO-certified DIMMs include optimised timings that optimise the performance of its <a href="Zen_4" title="Zen 4">Zen 4</a> processors.<a href="#cite_note-36">[36]</a> Unlike Intel's closed standard XMP, the EXPO standard is open and royalty-free.<a href="#cite_note-JRoachDigitalTrends-35">[35]</a> It can be used on Intel platforms.<a href="#cite_note-JRoachDigitalTrends-35">[35]</a> At launch in September 2022, there are 15 partner RAM kits with EXPO-certification available reaching up to 6400 MT/s.<a href="#cite_note-37">[37]</a>

<div class="mw-heading mw-heading3"><h3 id="Vendor-specific_memory">Vendor-specific memory</h3></div>

A common misuse is to write information to certain memory regions to bind vendor-specific memory modules to a specific system. <a href="Fujitsu_Technology_Solutions" title="Fujitsu Technology Solutions">Fujitsu Technology Solutions</a> is known to do this. Adding different memory module to the system usually results in a refusal or other counter-measures (like pressing F1 on every boot).

<pre>02 0E 00 01-00 00 00 EF-02 03 19 4D-BC 47 C3 46 ...........M.G.F

53 43 00 04-EF 4F 8D 1F-00 01 70 00-01 03 C1 CF SC...O....p.....

</pre>

This is the output of a 512 MB memory module from Micron Technologies, branded for Fujitsu-Siemens Computers, note the "FSC" string.

The system BIOS rejects memory modules that don't have this information starting at offset 128h.

Some Packard Bell AMD laptops also use this method, in this case the symptoms can vary but it can lead to a flashing cursor rather than a beep pattern. Incidentally this can also be a symptom of BIOS corruption as well.<a href="#cite_note-38">[38]</a> Though upgrading a 2 GB to a 4 GB can also lead to issues.

<div class="mw-heading mw-heading2"><h2 id="Reading_and_writing_SPD_information">Reading and writing SPD information</h2></div>

Memory module manufacturers write the SPD information to the <a href="EEPROM" title="EEPROM">EEPROM</a> on the module. Motherboard <a href="BIOS" title="BIOS">BIOSes</a> read the SPD information to configure the memory controller. There exist several programs that are able to read and modify SPD information on most, but not all motherboard chipsets.

<ul><li><a rel="nofollow" class="external text" href="http://www.nongnu.org/dmidecode/">dmidecode</a> program that can decode information about memory (and other things) and runs on <a href="Linux" title="Linux">Linux</a>, <a href="FreeBSD" title="FreeBSD">FreeBSD</a>, <a href="NetBSD" title="NetBSD">NetBSD</a>, <a href="OpenBSD" title="OpenBSD">OpenBSD</a>, <a href="BeOS" title="BeOS">BeOS</a>, <a href="Cygwin" title="Cygwin">Cygwin</a> and <a href="Solaris_(operating_system)" class="mw-redirect" title="Solaris (operating system)">Solaris</a>. dmidecode does not access SPD information directly; it reports the <a href="SMBIOS" class="mw-redirect" title="SMBIOS">SMBIOS</a> data about the memory.<a href="#cite_note-39">[39]</a> This information may be limited or incorrect.</li>

<li>On <a href="Linux" title="Linux">Linux</a> systems and <a href="FreeBSD" title="FreeBSD">FreeBSD</a>, the <a href="User_space" class="mw-redirect" title="User space">user space</a> program decode-dimms provided by i2c-tools decodes and prints information on any memory with SPD information in the computer.<a href="#cite_note-40">[40]</a><a href="#cite_note-41">[41]</a> It requires <a href="System_Management_Bus" title="System Management Bus">SMBus</a> controller support in the kernel, the EEPROM kernel driver, and also that the SPD EEPROMs are connected to the SMBus. On older Linux distributions, decode-dimms.pl was available as part of <a href="Lm_sensors" title="Lm sensors">lm_sensors</a>.</li>

<li>OpenBSD has included a driver (<a rel="nofollow" class="external text" href="https://man.openbsd.org/spdmem.4">spdmem(4)</a>) since version 4.3 to provide information about memory modules. The driver was ported from NetBSD, where it is available since release 5.0.</li>

<li><a href="Coreboot" title="Coreboot">Coreboot</a> reads and uses SPD information to initialize all <a href="Memory_controller" title="Memory controller">memory controllers</a> in a computer with timing, size and other properties.</li>

<li><a href="Microsoft_Windows" title="Microsoft Windows">Windows</a> systems use programs like <a href="HWiNFO" class="mw-redirect" title="HWiNFO">HWiNFO</a>,<a href="#cite_note-42">[42]</a> <a href="CPU-Z" title="CPU-Z">CPU-Z</a> and <a href="Speccy" title="Speccy">Speccy</a>, which can read and display DRAM module information from SPD.</li></ul>

Chipset-independent reading and writing of SPD information is done by accessing the memory's EEPROM directly with eeprom programmer hardware and software.

A not so common use for old laptops is as generic SMBus readers, as the internal EEPROM on the module can be disabled once the BIOS has read it so the bus is essentially available for use. The method used is to pull low the A0,A1 lines so the internal memory shuts down, allowing the external device to access the SMBus. Once this is done, a custom Linux build or DOS application can then access the external device. A common use is recovering data from LCD panel memory chips to retrofit a generic panel into a proprietary laptop.

On some chips it is also a good idea to separate write protect lines so that the onboard chips do not get wiped during reprogramming.

A related technique is rewriting the chip on webcams often included with many laptops as the bus speed is substantially higher and can even be modified so that 25x compatible chips can be read back for later cloning of the uEFI in the event of a chip failure.

This unfortunately only works on DDR3 and below, as DDR4 uses different security and can usually only be read. Its possible to use a tool like SPDTool or similar and replace the chip with one that has its WP line free so it can be altered in situ.

On some chipsets the message "Incompatible SMBus driver?" may be seen so read is also prevented.

<div class="mw-heading mw-heading3"><h3 id="RGB_LED_control">RGB LED control</h3></div>

Some memory modules (especially on <a href="Gaming_PC" class="mw-redirect" title="Gaming PC">Gaming PCs</a>)<a href="#cite_note-43">[43]</a> support RGB LEDs that are controlled by proprietary SMBus commands. This allows LED color control without additional connectors and cables. Kernel drivers from multiple manufacturers required to control the lights have been exploited to gain access ranging from full kernel memory access, to MSR and I/O port control numerous times in 2020 alone.<a href="#cite_note-44">[44]</a><a href="#cite_note-45">[45]</a><a href="#cite_note-46">[46]</a>

<div class="mw-heading mw-heading2"><h2 id="On_older_equipment">On older equipment</h2></div>

Some older equipment require the use of <a href="SIMM" title="SIMM">SIMMs</a> with parallel presence detect (more commonly called simply presence detect or PD). Some of this equipment uses non-standard PD coding, <a href="IBM" title="IBM">IBM</a> computers and <a href="Hewlett-Packard" title="Hewlett-Packard">Hewlett-Packard</a> <a href="LaserJet" class="mw-redirect" title="LaserJet">LaserJet</a> and other printers in particular.

<ul><li><a href="Transducer_electronic_data_sheet" class="mw-redirect" title="Transducer electronic data sheet">Transducer electronic data sheet</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFThomas_P._KoenigNathan_John1997" class="citation cs2">Thomas P. Koenig; Nathan John (3 February 1997), <a rel="nofollow" class="external text" href="http://findarticles.com/p/articles/mi_m0EKF/is_n2153_v43/ai_19102210/">"Serial Presence Detection poised for limelight"</a>, Electronic News, 43 (2153)</cite>

</li>

<li id="cite_note-2"><a href="#cite_ref-2">^</a> <a rel="nofollow" class="external text" href="http://www.jedec.org/sites/default/files/docs/4_01_04R21.pdf">JEDEC Standard 21-C section 4.1.4</a> "Definition of the TSE2002av Serial Presence Detect (SPD) EEPROM with Temperature Sensor (TS) for Memory Module Applications"

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.micron.com/-/media/client/global/documents/products/technical-note/dram-modules/tn_04_42.pdf">"TN-04-42: Memory Module Serial Presence-Detect Write Protection"</a> (PDF). Micron.</cite>

</li>

<li id="cite_note-4"><a href="#cite_ref-4">^</a> <cite id="CITEREFDean_Kent1998" class="citation web cs1">Dean Kent (24 October 1998). <a rel="nofollow" class="external text" href="https://www.tomshardware.com/reviews/ram-guide,89.html">"Ram Guide"</a>. Tom's Hardware.</cite>

</li>

<li id="cite_note-5"><a href="#cite_ref-5">^</a> <cite id="CITEREFShimpi" class="citation web cs1">Shimpi, Anand Lal. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110524185521/http://www.anandtech.com/show/60">"PC100 SDRAM: An Introduction"</a>. www.anandtech.com. Archived from <a rel="nofollow" class="external text" href="https://www.anandtech.com/show/60">the original</a> on 24 May 2011.</cite>

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> <a rel="nofollow" class="external text" href="http://www.memorytesters.com/ramcheck/rc_ap3.htm">Application note INN-8668-APN3: SDRAM SPD Data Standards</a>, memorytesters.com

</li>

<li id="cite_note-spd_pc100-7"><a href="#cite_ref-spd_pc100_7-0">^</a> <cite class="citation cs2"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20140531124526/http://www.taricorp.net/wp-content/uploads/2012/04/SPDSDRAM1.2a1.pdf">PC SDRAM Serial Presence Detect (SPD) Specification</a> (PDF), 1.2A, December 1997, p. 28, archived from <a rel="nofollow" class="external text" href="http://www.taricorp.net/wp-content/uploads/2012/04/SPDSDRAM1.2a1.pdf">the original</a> (PDF) on 31 May 2014, retrieved 30 May 2014</cite>

</li>

<li id="cite_note-spd_ddr-8">^ <a href="#cite_ref-spd_ddr_8-0">a</a> <a href="#cite_ref-spd_ddr_8-1">b</a> <a rel="nofollow" class="external text" href="http://www.jedec.org/download/search/4_01_02_04R13.PDF">JEDEC Standard 21-C section 4.1.2.4</a> "SPDs for DDR SDRAM"

</li>

<li id="cite_note-spd_ddr2-9">^ <a href="#cite_ref-spd_ddr2_9-0">a</a> <a href="#cite_ref-spd_ddr2_9-1">b</a> <a rel="nofollow" class="external text" href="http://www.jedec.org/download/search/4_01_02_10R13.pdf">JEDEC Standard 21-C section 4.1.2.10</a> "Specific SPDs for DDR2 SDRAM"

</li>

<li id="cite_note-10"><a href="#cite_ref-10">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20151222112142/http://www.simmtester.com/page/news/showpubnews.asp?num=153">"Understanding DDR3 Serial Presence Detect (SPD) Table"</a>. Archived from <a rel="nofollow" class="external text" href="http://www.simmtester.com/page/news/showpubnews.asp?num=153">the original</a> on 22 December 2015. Retrieved 29 May 2010.</cite>

</li>

<li id="cite_note-spd_ddr3_docs-11"><a href="#cite_ref-spd_ddr3_docs_11-0">^</a> <a rel="nofollow" class="external text" href="http://www.jedec.org/sites/default/files/docs/4_01_02_11R21.pdf">JESD21-C Annex K: Serial Presence Detect for DDR3 SDRAM Modules</a>, Release 4, SPD Revision 1.1

</li>

<li id="cite_note-12"><a href="#cite_ref-12">^</a> <a rel="nofollow" class="external text" href="http://www.softnology.biz/pdf/JEDEC_DDR3_SPD_4_01_02_11R24.pdf">JESD21-C Annex K: Serial Presence Detect for DDR3 SDRAM Modules</a>, Release 6, SPD Revision 1.3

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> <cite id="CITEREFDelvare" class="citation web cs1">Delvare, Jean. <a rel="nofollow" class="external text" href="https://lkml.org/lkml/2017/11/20/131">"[PATCH] eeprom: New ee1004 driver for DDR4 memory"</a>. LKML. Retrieved 7 November 2019.</cite>

</li>

<li id="cite_note-annex_l-14">^ <a href="#cite_ref-annex_l_14-0">a</a> <a href="#cite_ref-annex_l_14-1">b</a> <cite id="CITEREFJEDEC" class="citation web cs1">JEDEC. <a rel="nofollow" class="external text" href="http://www.softnology.biz/pdf/4_01_02_AnnexL-R25_SPD_for_DDR4_SDRAM_Release_3_Sep2015.pdf">"Annex L: Serial Presence Detect (SPD) for DDR4 SDRAM Modules"</a> (PDF).</cite>

</li>

<li id="cite_note-TSE2004-15"><a href="#cite_ref-TSE2004_15-0">^</a> <cite id="CITEREFJEDEC" class="citation web cs1">JEDEC. <a rel="nofollow" class="external text" href="http://www.softnology.biz/pdf/ee1004_tse2004.pdf">"EE1004 and TSE2004 Device Specification (Draft)"</a> (PDF). Retrieved 7 November 2019.</cite>

</li>

<li id="cite_note-spd_ddr4_docs-16"><a href="#cite_ref-spd_ddr4_docs_16-0">^</a> <a rel="nofollow" class="external text" href="https://www.jedec.org/system/files/docs/4_01_02_AnnexL-5R29.pdf">JESD21-C Annex L: Serial Presence Detect for DDR4 SDRAM Modules</a>, Release 5

</li>

<li id="cite_note-17"><a href="#cite_ref-17">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.jedec.org/standards-documents/docs/jesd400-5b">"JESD400-5B(JESD400-5B)"</a>. jedec. 2023. Retrieved 31 December 2023.</cite>

</li>

<li id="cite_note-spd_ddr3-18"><a href="#cite_ref-spd_ddr3_18-0">^</a> <a rel="nofollow" class="external text" href="http://www.jedec.org/download/search/4_01_02_11R18.pdf">JEDEC Standard 21-C section 4.1.2.11</a> "Serial Presence Detect (SPD) for DDR3 SDRAM Modules"

</li>

<li id="cite_note-spd_base-19"><a href="#cite_ref-spd_base_19-0">^</a> <a rel="nofollow" class="external text" href="http://www.jedec.org/download/search/4_01_02_00r9.pdf">JEDEC Standard 21-C section 4.1.2</a> "SERIAL PRESENCE DETECT STANDARD, General Standard"

</li>

<li id="cite_note-spd_sdr-20"><a href="#cite_ref-spd_sdr_20-0">^</a> <a rel="nofollow" class="external text" href="http://www.jedec.org/download/search/4_01_02_05R12.PDF">JEDEC Standard 21-C section 4.1.2.5</a> "Specific PDs for Synchronous DRAM (SDRAM)"

</li>

<li id="cite_note-21"><a href="#cite_ref-21">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.howtogeek.com/what-is-xmp/">"What Is XMP, and Why Does It Matter for RAM?"</a>. How-To Geek. 21 September 2023. Retrieved 19 May 2025.</cite>

</li>

<li id="cite_note-22"><a href="#cite_ref-22">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.pcworld.com/article/394250/why-xmp-and-memory-overclocking-are-ok-even-if-they-void-your-warranty.html">"Why XMP and memory overclocking are OK even if they void your warranty"</a>. PCWorld. 16 March 2021. Retrieved 19 May 2025.</cite>

</li>

<li id="cite_note-23"><a href="#cite_ref-23">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.tomshardware.com/news/amd-ryzen-7000-burning-out-root-cause-identified-expo-and-soc-voltages-to-blame">"AMD Ryzen 7000 Burning Out: EXPO and SoC Voltages to Blame (AMD Responds)"</a>. Tom's Hardware. 25 April 2023. Retrieved 19 May 2025.</cite>

</li>

<li id="cite_note-24"><a href="#cite_ref-24">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.intel.com/content/www/us/en/gaming/extreme-memory-profile-xmp.html">"Intel® Extreme Memory Profile (Intel® XMP)"</a>. Intel. Retrieved 19 May 2025. <q>Altering clock frequency or voltage may damage or reduce the useful life of the processor and other system components, and may reduce system stability and performance. Product warranties may not apply if the processor is operated beyond its specifications.</q></cite>

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> <cite class="citation cs2"><a rel="nofollow" class="external text" href="http://www.nvidia.com/content/epp/epp_specifications.pdf">DDR2 UDIMM Enhanced Performance Profiles Design Specification</a> (PDF), <a href="Nvidia" title="Nvidia">Nvidia</a>, 12 May 2006, retrieved 5 May 2009</cite>

</li>

<li id="cite_note-26"><a href="#cite_ref-26">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20081207172621/http://www.nvidia.com/docs/CP/45121/sli_memory.pdf">"Technical Brief - SLI-Ready Memory with Enhanced Performance Profiles One-Click Hassle-Free Memory Performance Boost"</a> (PDF). Archived from <a rel="nofollow" class="external text" href="http://www.nvidia.com/docs/CP/45121/sli_memory.pdf">the original</a> (PDF) on 7 December 2008.</cite>

</li>

<li id="cite_note-27"><a href="#cite_ref-27">^</a> <a rel="nofollow" class="external text" href="http://www.nvidia.com/docs/IO/52280/NVIDIA_EPP2_TB.pdf">Enhanced Performance Profiles 2.0</a> (pp. 2–3)

</li>

<li id="cite_note-28"><a href="#cite_ref-28">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.intel.co.uk/content/www/uk/en/gaming/extreme-memory-profile-xmp.html">"What Is Intel Extreme Memory Profile (Intel XMP)?"</a>. Intel. Retrieved 26 September 2022.</cite>

</li>

<li id="cite_note-29"><a href="#cite_ref-29">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.amd.com/en/technologies/amp">"Memory Profile Technology - AMP up your RAM"</a>. AMD. 2012. Retrieved 8 January 2018.</cite>

</li>

<li id="cite_note-30"><a href="#cite_ref-30">^</a> <cite id="CITEREFMartin2012" class="citation web cs1">Martin, Ryan (23 July 2012). <a rel="nofollow" class="external text" href="https://www.eteknix.com/amd-introduces-its-xmp-equivalent-amp/">"AMD introduces its XMP-equivalent AMP - eTeknix"</a>. eTeknix. Retrieved 8 January 2018.</cite>

</li>

<li id="cite_note-31"><a href="#cite_ref-31">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.msi.com/news/detail/0ec96be397dd6d3cf2fecb4a2d627c1c">"MSI is worlds first brand to enable A-XMP on Ryzen for best DDR4 performance, launches new models"</a>. MSI. 21 March 2017. Retrieved 8 January 2018.</cite>

</li>

<li id="cite_note-32"><a href="#cite_ref-32">^</a> <cite id="CITEREFTradesman12016" class="citation web cs1">Tradesman1 (26 August 2016). <a rel="nofollow" class="external text" href="http://www.tomshardware.com/answers/id-3167421/xmp-docp-eocp.html#r18503260">"What does XMP, DOCP, EOCP mean - Solved - Memory"</a>. Tom's Hardware Forums. Retrieved 8 January 2018.</cite><code class="cs1-code">{{cite web}}</code>: CS1 maint: numeric names: authors list (link)

</li>

<li id="cite_note-xmp1.1-33">^ <a href="#cite_ref-xmp1.1_33-0">a</a> <a href="#cite_ref-xmp1.1_33-1">b</a> <a href="#cite_ref-xmp1.1_33-2">c</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120306230940/http://www.softnology.biz/pdf/IntelXMP_Rev1.1.pdf">"Intel Extreme Memory Profile (XMP) Specification, Rev 1.1"</a> (PDF). Intel. October 2007. Archived from <a rel="nofollow" class="external text" href="http://www.softnology.biz/pdf/Intel_XMP_Spec_Rev1.1.pdf">the original</a> (PDF) on 6 March 2012. Retrieved 25 May 2010.</cite>

</li>

<li id="cite_note-34"><a href="#cite_ref-34">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.amd.com/en/technologies/expo">"AMD Extended Profiles for Overclocking"</a>. AMD. Retrieved 26 September 2022.</cite>

</li>

<li id="cite_note-JRoachDigitalTrends-35">^ <a href="#cite_ref-JRoachDigitalTrends_35-0">a</a> <a href="#cite_ref-JRoachDigitalTrends_35-1">b</a> <a href="#cite_ref-JRoachDigitalTrends_35-2">c</a> <cite id="CITEREFRoach2022" class="citation web cs1">Roach, Jacob (6 September 2022). <a rel="nofollow" class="external text" href="https://www.digitaltrends.com/computing/what-is-amd-expo/">"What is AMD EXPO and should my DDR5 have it?"</a>. Digital Trends. Retrieved 26 September 2022.</cite>

</li>

<li id="cite_note-36"><a href="#cite_ref-36">^</a> <cite id="CITEREFBonshor2022" class="citation web cs1">Bonshor, Gavin (30 August 2022). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20220830224541/https://www.anandtech.com/show/17556/amd-expo-memory-one-click-overclocking-profiles-for-ryzen-7000-feat-gskill-and-corsair">"AMD EXPO Memory Technology: One Click Overclocking Profiles For Ryzen 7000"</a>. AnandTech. Archived from <a rel="nofollow" class="external text" href="https://www.anandtech.com/show/17556/amd-expo-memory-one-click-overclocking-profiles-for-ryzen-7000-feat-gskill-and-corsair">the original</a> on 30 August 2022. Retrieved 26 September 2022.</cite>

</li>

<li id="cite_note-37"><a href="#cite_ref-37">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://videocardz.com/newz/amd-announces-expo-technology-for-ddr5-memory-overclocking">"AMD announces EXPO technology for DDR5 memory overclocking"</a>. VideoCardz. 30 August 2022. Retrieved 26 September 2022.</cite>

</li>

<li id="cite_note-38"><a href="#cite_ref-38">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://forums.tomshardware.com/threads/packard-bell-lj65-ram-upgrade.1651388/">"Packard Bell LJ65 RAM upgrade"</a>. Tom's Hardware Forum. 9 January 2014.</cite>

</li>

<li id="cite_note-39"><a href="#cite_ref-39">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.linux.com/news/dmidecode-whats-it-good">"dmidecode: What's it good for?"</a>. Linux.com | The source for Linux information. 29 November 2004.</cite>

</li>

<li id="cite_note-40"><a href="#cite_ref-40">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://manpages.debian.org/testing/i2c-tools/decode-dimms.1.en.html">"decode-dimms(1)"</a>. Debian Manpage. Retrieved 16 December 2020.</cite>

</li>

<li id="cite_note-41"><a href="#cite_ref-41">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.freebsd.org/cgi/man.cgi?query=decode-dimms">"decode-dimms"</a>. www.freebsd.org. Retrieved 24 January 2021.</cite>

</li>

<li id="cite_note-42"><a href="#cite_ref-42">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.hwinfo.com/">"HWiNFO - Professional System Information and Diagnostics"</a>. HWiNFO.</cite>

</li>

<li id="cite_note-43"><a href="#cite_ref-43">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.corsair.com/us/en/vengeance-rgb-pro-memory">"VENGEANCE RGB PRO series DDR4 memory | Desktop Memory | CORSAIR"</a>. www.corsair.com. Retrieved 26 November 2020.</cite>

</li>

<li id="cite_note-44"><a href="#cite_ref-44">^</a> <cite id="CITEREFActiveCyber" class="citation techreport cs1">ActiveCyber. <a rel="nofollow" class="external text" href="https://www.activecyber.us/activelabs/viper-rgb-driver-local-privilege-escalation-cve-2019-18845">Viper RGB Driver Local Privilege Escalation</a> (Technical report). <a href="CVE_(identifier)" class="mw-redirect" title="CVE (identifier)">CVE</a>-<a rel="nofollow" class="external text" href="https://nvd.nist.gov/vuln/detail/CVE-2019-18845">2019-18845</a> – via MITRE Corporation.</cite>

</li>

<li id="cite_note-45"><a href="#cite_ref-45">^</a> <cite id="CITEREFActiveCyber" class="citation techreport cs1">ActiveCyber. <a rel="nofollow" class="external text" href="https://www.activecyber.us/activelabs/corsair-icue-driver-local-privilege-escalation-cve-2020-8808">CORSAIR iCUE Driver Local Privilege Escalation (CVE-2020-8808)</a> (Technical report). <a href="CVE_(identifier)" class="mw-redirect" title="CVE (identifier)">CVE</a>-<a rel="nofollow" class="external text" href="https://nvd.nist.gov/vuln/detail/CVE-2020-8808">2020-8808</a> – via MITRE Corporation.</cite>

</li>

<li id="cite_note-46"><a href="#cite_ref-46">^</a> <cite id="CITEREFActiveCyber" class="citation techreport cs1">ActiveCyber. <a rel="nofollow" class="external text" href="https://www.activecyber.us/activelabs/active-2020-003-trident-z-lighting-control-driver-local-privilege-escalation">ACTIVE-2020-003: Trident Z Lighting Control Driver Local Privilege Escalation</a> (Technical report). <a href="CVE_(identifier)" class="mw-redirect" title="CVE (identifier)">CVE</a>-<a rel="nofollow" class="external text" href="https://nvd.nist.gov/vuln/detail/CVE-2020-12446">2020-12446</a> – via MITRE Corporation.</cite>

</li>

</ol></div></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-08-06" href="https://en.wikipedia.org/wiki/?title=Serial_presence_detect&oldid=1304464467">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>